[FLINK-38840][postgres] Postgres YAML connector supports emitting complete Table ID#4209
Conversation
github-actions
Bot
added
postgres-cdc-connector
postgres-pipeline-connector
docs
|
@yuxiqian PTAL |
…plete Table ID [FLINK-38840][postgres] Postgres YAML connector supports emitting complete Table ID [FLINK-38840][postgres] Postgres YAML connector supports emitting complete Table ID [FLINK-38840][postgres] Postgres YAML connector supports emitting complete Table ID
I'm a little concerned about changing default Table ID format. It may affect transform & route table matching rules and schema registry states where Table IDs are used as key. |
We still need to control the output of the full tableID through configuration to ensure that it is compatible with production |
yuxiqian
left a comment
yuxiqian
left a comment
There was a problem hiding this comment.
Changes LGTM. Would @loserwang1024 like to take another look?
|
@loserwang1024 PTLK |
|
LGTM |
…plete Table ID (apache#4209) added a new option `table-id.include-database` to emit (db, schema, table) style table id.
3 participants
Currently, Postgres YAML connector maps (schema, table) as Pipeline event Table ID, and the database part is missing.
We may add a new option to generate complete Table ID (database, schema, table). This could be useful when records are written into Kafka as JSON messages.